Correct escape characters in grep command#966
Merged
glittercowboy merged 1 commit intogsd-build:mainfrom Mar 15, 2026
Merged
Conversation
Fix escape characters in grep command for extracting code interfaces.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix escape characters in grep command for extracting code interfaces.
What
Fix invalid TOML escape sequences in GSD agent prompts by properly escaping backslashes in embedded
grepexamples, so planning/research roles load correctly.Why
Unescaped backslashes made multiple
gsd-*.tomlfiles fail parsing, which caused roles likegsd-plannerto be unavailable and forced fallback behavior.Testing
Checklist
Breaking Changes
None